Skip to main content

Console Application

A console application in the context of EmpowerID is a developer tool used to interact with the EmpowerID database (meta-directory). It provides a simple and efficient way to perform database operations such as retrieving, inserting, and updating records.

Here are some key points about EmpowerID console applications​

1. Visual Studio Integration​

  • Creating a console application in Workflow Studio automatically opens it as a project in Visual Studio, allowing developers to leverage its features for efficient code development. (Confirm this point)

2. Pre-configured Environment​

  • The console application project in Visual Studio comes pre-configured with references to Empower ID assemblies.

  • The main class template includes default namespaces and components.

3. Components and Database Interaction​

  • The components namespace provides class libraries that act as a data access layer for the Empower ID meta-directory (SQL database).

  • Developers should use these components instead of creating their own custom data access layers. Each database table typically has a corresponding class in components, which includes methods for retrieving, inserting, and updating records.

Example:

components.Person.GetByPersonID(personID);

This method retrieves a Person record based on personID without requiring direct interaction with stored procedures.

4. Views vs. Components​

  • When you query a view, the results are filtered based on the security context of the caller, showing only the data the caller has permission to see.
  • Component methods provide direct database access without security trimming.

You should choose between using a component or a view based on whether security trimming is required for your operation

  • List Encapsulation:
    • Components return lists encapsulated in Tlist.
    • Views return lists encapsulated in Vlist.

5. Automatic Configuration​

  • The necessary database connection settings are automatically configured.
  • Connection details are stored in:
    • System registry (under the Empower ID entries).
    • Application configuration files.
  • Developers typically don’t need to manually configure connection strings.

6. Use Cases​

Testing Empower ID Components: Console applications help validate data access logic before integrating into workflows or APIs.

Simplified Data Access: Pre-built components streamline database interactions, reducing development complexity.

Summary​

EmpowerID console applications provide a developer-friendly approach to interacting with the database, utilizing pre-configured components and simplifying data access, security, and testing.